home *** CD-ROM | disk | FTP | other *** search
-
- IETF STEERING GROUP (IESG)
-
- REPORT FROM THE TELECONFERENCE
-
- August 31th, 1992
-
- Reported by: Greg Vaudreuil, IESG Secretary
-
- This report contains IESG meeting notes, positions and action items.
- For more information please contact the IESG Secretary.
-
- iesg-secretary@nri.reston.va.us
-
- ATTENDEES
- ---------
-
- Almquist, Philip / Consultant
- Borman, David / Cray Research
- Crocker, Dave / TBO
- Crocker, Steve / TIS
- Coya, Steve / CNRI
- Gross, Philip / ANS
- Hinden, Robert / SUN
- Huizer, Erik / SURFnet
- Reynolds, Joyce / ISI
- Stockman, Bernard / SUNET/NORDUnet
- Vaudreuil, Greg / CNRI
-
- Regrets
- Davin, Chuck / MIT
- Hobby, Russ /UC-Davis
- Piscitello, Dave/ Bellcore
-
-
-
- AGENDA
- ------
-
- o Administrivia
- o Role Call
- o Bash the Agenda
- o Review outstanding minutes
-
- o Protocol Actions
- o String Representation of Distinguished Names
- o Using X.500 for User Friendly Naming
- o SNMP over OSI
- o SNMP over Appletalk
- o Generic Interface MIB
- o Token Ring MIB
- o Token Bus MIB
- o Dynamic Host Configuration
- o Dynamic Host Configuration Options
- o Interoperation between BOOTP and DHC
- o PPP LCP for Decnet IV
- o Compressing TCP/IP headers
- o SMTP extensions for 8 bit Transport
-
- o Technical Management Issues
- o Process Working Group
- o SMP Chairman
- o IETF Meeting schedule
-
- MINUTES
- -------
-
- 1) Administrivia
-
- o Bash the agenda
-
- This meeting was planned to discuss the many protocol actions
- received in the last month.
-
- o Approval of the Minutes
-
- The minutes of the August 10th and August 17th meetings were
- approved.
-
- o Next Meeting
-
- The next meeting is scheduled for September 10th, 12-2 ET.
-
- 2) Protocol Actions.
-
- o String Representation of Distinguished Names
-
- This document is still waiting for an update by Steve
- Hardcastle-Kille
-
- o Using X.500 for User Friendly Naming
-
- The IESG issued a last call for this experimental document to
- solicit comments. There were no objections to making this
- experimental rather than Proposed Standard.
-
- ACTION: Vaudreuil -- Send a Notification to the RFC Editor recommending
- the publication of the Internet Draft "Using the OSI Directory to
- Achieve User Friendly Naming" as an Experimental protocol.
-
- o SNMP over OSI
- o SNMP over Appletalk
-
- Dave Piscitello was not present at this conference and the IESG
- deferred discussion of these documents.
-
- o Generic Interface MIB
- o Token Ring MIB
- o Token Bus MIB
-
- Chuck Davin was not present at this conference. A question about
- the implementation experience of these MIBS was raised, prompting
- Davin to send a second note to the IETF requesting implementation
- experience. The response has been minimal.
-
- o Dynamic Host Configuration
- o Dynamic Host Configuration Options
- o Interoperability between BOOTP and DHC
-
- The Dynamic Host Configuration documents have taken a long time to
- be completed at a first review indicates additional editorial work
- may be needed. Several problems are addressed in these protocol,
- including one not originally intended, enabling more efficient CIDR
- addressing. To insure that these solutions are well architected,
- the IESG has requested that Almquist and Hinden work to assemble an
- informal review team to check these documents.
-
- ACTION: Hinden -- Solicit reviewers for the DHC Internet Drafts to
- confirm the architectural integration of the various pieces.
-
-
- ACTION: Stockman -- Review the Bootp documents for addressing content
- and CIDR compatibility.
-
- ACTION: Gross -- Solicit comments on DHC from the BGP community.
-
- A fourth document, "Clarifications and Extensions to BOOTP" was not
- listed in the last call. This document should be part of the set.
-
- ACTION: Vaudreuil -- Get an updated version of the BOOTP clarifications
- document posted as an Internet Draft and when ready, send a Last Call.
-
- o PPP LCP for Decnet
-
- The IESG had not reviewed this protocol yet and deferred
- discussion.
-
- o Compression TCP/IP Headers
-
- There was no progress to report.
-
- o SMTP Extensions for 8 bit Transport
-
- There were significant comments received from the Last Call on these
- documents. The comments ranged from the general to the specific,
- and most had concerns about the complexity of the protocol. The
- IESG discussed the comments and agreed they were serious enough that
- the document should be sent back to the Working Group for
- re-evaluation.
-
- The IESG briefly discussed the process by which it sends a document
- back for the Working Group and agreed on the following points. The
- have been a lot of comments, indicating consensus may not have been
- reached. An common concern is that of complexity and the Working
- Group should review the design choices which resulted in the current
- specification. All comments should be answered and all commenters
- should be given an opportunity to participate in the dialogue.
-
- ACTION: Vaudreuil -- Write and send to the IESG a note to be sent to the SMTP Extensions working group. After incorporating comments, send
- the note Tuesday.
-
- 3) Technical Management Issue:
-
- o Process Working Group
-
- The IESG reviewed the latest version of the proposed charter and was
- satisfied.
-
- ACTION: Vaudreuil -- After a IAB comment period on the POISED Working
- Group, send the charter of the POISED Working Group to the IETF list.
-
- o SMP Chairmanship
-
- The IESG affirmed Davin's choice of Bob Stewart as chairman of the
- SMP Working group.
-
- ACTION: Davin -- Submit a charter for the SMP Working Group to the IESG
- for review.
-
- o IETF Plenary Meeting Agenda
-
- The IESG re-organized the IETF plenary schedule to accommodate the
- greater than normal demand for plenary presentation slots needed for
- reporting of ROAD activity. The morning working group slot on
- Monday will be converted to ROAD Plenary presentations. The Open
- IESG session will be devoted to discussion of ROAD proposals. The
- Friday Area Director Reports will be converted to Working Group
- sessions. Area Reports will be submitted electronically to the
- community within a week of the meeting.
-
-